Skip to content

fix(dev-box): pin the image rebuilt from sha-7725235 - #173

Open
Leechael wants to merge 1 commit into
mainfrom
dev-box/bump-digest
Open

Leechael wants to merge 1 commit into
mainfrom
dev-box/bump-digest

Conversation

@Leechael

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #172: bump the pinned dev-box image to the build that actually contains it.

sha-5a930ae predates both changes in #172 (port 22, user_config key merge), so the example as published still pulled the old container — 1022, env-only keys. 7725235 is the merge commit of #172, and its main build (run 43372595906) produced the image below.

Tag ghcr.io/dstack-tee/dstack-dev-box:sha-7725235 (also latest)
Digest sha256:0dc661ea51fcbd70007d117b9e60883d9a96bac510a80683f5bdd6b7947b0291
Built 2026-11-13T05:32:25Z

Both the compose file and the README snippet are updated, so the copy-paste path and the example agree.

Verification

  • grep for the old tag/digest across the repo: no remaining references.
  • Digest taken from the registry (GET /orgs/Dstack-TEE/packages/container/dstack-dev-box/versions) and cross-checked against the build log's containerimage.digest.
  • Pinning by digest keeps the attested app-compose identifying one exact image; the tag keeps it readable.

Same shape as #170.

The previous pin, sha-5a930ae, predates the port 22 change and the
user_config key merge, so the published example still shipped the old
container. 7725235 is the merge commit whose main build produced
sha-7725235 / latest on GHCR, with digest
sha256:0dc661ea51fcbd70007d117b9e60883d9a96bac510a80683f5bdd6b7947b0291.

Pinning the digest keeps the attested app-compose identifying one exact
image while the tag keeps it readable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant